-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Eks integ tests #77
Eks integ tests #77
Conversation
@@ -123,9 +123,6 @@ jobs: | |||
- # issue #49 | |||
app_to_test: ts-eks-helm | |||
mode: upgrade |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume this one is still broken because of #48? (If so, let's update line 123 just for completeness)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well its broken because our current release branch is broken mainly. So we need 2 releases then can enable this and the helm one.
lb = new aws.lb.LoadBalancer(`${appName}-${resourceId}-alb`, { | ||
name: `${appName}-${resourceId}`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this (and similar) conflict with @DavidSeptimus-Klotho's work? If so, probably just need to coordinate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i mentioned i was doing this to him, he said he hadnt touched these modules yet so should be good
|
Only change properties when it's coming from solution
• Does any part of it require special attention?
• Does it relate to or fix any issue? closes #69 and closes #76
Did some naming fixes to prevent running into conflicts in our test. None of the naming fixes are external resources so it is backwards compatible, the user shouldnt even notice outside of pulumi preview.
Had to modify our kubeconfig logic due to the pulumi bug
adding just the fresh tests back. Upgrade will fail due to the released version having this bug so we can add those back in 2 releases.
Standard checks